Web Application Directory Trouble Screen

Unsuccessful Directory searches occur for several reasons. For example, an inability to connect to the server for a search or finding no Directory listings that match the search criteria produce unsuccessful searches. Any search-related problem displays as an error message on the Directory Trouble screen, shown in Figure 31.

Possible reasons for search failure and the resulting messages displayed on the Trouble screen follow in Table 12.

Table 12: Search Failure Causes and Corresponding Trouble Screen
Error Messages
Cause of Search Failure	LDAP Result Code	Trouble Screen Message
N/A. The corresponding LDAP Result Code represents a successful search.	0	No message displayed. The search was successful.
Operations/Protocol error.	1, 2	Operations/Protocol error.
Server-generated timeout.	3	Server timed out.
More than 96 entries match the Search criteria.	4	Size limit exceeded.
Various unexpected errors. You should never receive these result codes.	5, 6, 10, 11, 12, 13, 14, 18, 19, 20, 21, 34, 36, 54, 64, 65, 66, 67, 68, 69, 71	Invalid response.
Authentication not accepted.	7, 8, 48, 49, 50, 53	Authentication error.
Telephone Number not recognized.	16, 17	Telephone Number not recognized.
Object not found.	32	No results found.
Server responds with “null” as data.	N/A	No results found.
Server not available.	51, 52	Server not available.
Other, unspecified failure.	80	An unknown problem has occurred.
If any of these system values are null (except DIRUSERID and DIRSRVRPWD, which are optional and might remain null), and the user tries to access the Directory application, the endpoint receives a Trouble Screen.	N/A	Insufficient Administrative Information.
The Directory server does not respond at all within an administrable amount of seconds. The default is 10 seconds.	N/A	Unable to contact server.
When the Directory application receives a request for a Search screen, it sends a Search screen in response only if supplied with the minimum administrative information. Otherwise, the endpoint receives a Trouble Screen.	N/A	Insufficient Administrative Information.
When the Directory application receives a request for a search from an endpoint, it initiates a connection to the directory database server. If the connection succeeds, a query is formatted and sent to the database server based on the input received from the endpoint. If the input received from the endpoint is null, the endpoint receives a Trouble Screen.	N/A	Insufficient Query Information.
If a connection to the database server cannot be established, or if the connection fails before a response is received, the endpoint receives a Trouble Screen.	N/A	Connection Failure.
When the Directory application receives a successful response from the database server, the endpoint receives a Successful Result screen. If no matching database entries are returned, the endpoint receives a No Match Result screen. If the database returns an error, the endpoint receives a Trouble screen.	N/A	No Match Result.
Cannot be determined.	9, 22 - 31, 35, 37 - 47, 55 - 63, 70, 72 - 79, and 81 - 90	Unknown Error.